Dynamic mobile wallet items

ABSTRACT

Various embodiments herein each include at least one of systems, methods, and software for dynamic mobile wallet items. One embodiment in the form of a method includes receiving, via a network, a dynamic mobile document request associated with a registered user and including a token associated with data to be included in the dynamic mobile document. The method may then retrieve data for the dynamic mobile document from a database based at least in part on the token and an identifier of the registered user and then continue by transmitting, via the network, the retrieved dynamic mobile document data and data indicating how the dynamic mobile document is to be provided to the registered user to a dynamic mobile document generation service, the dynamic mobile document generation service to generate and provide the dynamic mobile document to the registered user.

BACKGROUND INFORMATION

Consumers have the option to receive coupons, tickets, vouchers, andpasses as barcodes on their mobile devices. These mobile barcodesprovide convenience to the consumer. A wallet is a mobile applicationthat enables mobile tickets, mobile documents, coupons, vouchers, andthe like to he delivered and stored locally on the device itself. Thisdevice repository enables items to be located easily on a mobile deviceand opened-up for scanning without requiring a data connection.Travelers in locations where data connections are unavailable orinconvenient may prefer the wallet for its ability to store barcodesonboard for convenient retrieval.

SUMMARY

Various embodiments herein each include at least one of systems,methods, and software for dynamic mobile wallet items. One embodiment inthe form of a method includes receiving, via a network, a dynamic mobiledocument request associated with a registered user and including a tokenassociated with data to be included in the dynamic mobile document. Themethod may then retrieve data for the dynamic mobile document from adatabase based at least in part on the token and an identifier of theregistered user. The method then continues by transmitting, via thenetwork, the retrieved dynamic mobile document data and data indicatinghow the dynamic mobile document is to be provided to the registered userto a dynamic mobile document generation service. The dynamic mobiledocument generation service then generates and provides the dynamicmobile document to the registered user.

Another method embodiment, such as may be performed by a dynamic mobiledocument generation service, includes receiving, via a network from adata source, a dynamic mobile document generation request including dataidentifying a transmission mode for transmitting a dynamic mobiledocument to be generated, a network identifier of where to send thegenerated dynamic mobile document, and at least one data item to beincluded in the dynamic mobile document when generated and to uniquelyidentify the dynamic mobile document. This method then stores data ofthe dynamic mobile document generation request in a database andgenerates the dynamic mobile document including the at least one dataitem and metadata defining the at least one item as a dynamic data itemwithin the generated dynamic mobile document. This method may thenproceed by transmitting, via the network, the generated dynamic mobiledocument according to the identified transmission mode to a networkdestination of the network identifier.

Yet another embodiment, in the form of a system, includes at least onecomputer processor, at least one memory device, and at least one networkinterface device. The system of this embodiment also includes a databaseunder management by a database management system stored on the at leastone memory device or accessible via that at least one network interfacedevice. The database stores dynamic mobile document data received fromat least one data source. The system further includes a dynamic mobiledocument generation module stored in the at least one memory device andexecutable by the at least one processor to perform data processingactivities. The data processing activities of the dynamic documentgeneration module include receiving, via the at least one networkinterface device from the at least one data source, a dynamic mobiledocument generation request including data identifying a transmissionmode for transmitting a dynamic mobile document to be generated, anetwork identifier of where to send the generated dynamic mobiledocument, and at least one data item to be included in the dynamicmobile document when generated and to uniquely identify the dynamicmobile document. These data processing activities also include storingdata of the dynamic mobile document generation request in the databaseand generating the dynamic mobile document including the at least onedata item and metadata defining the at least one item as a dynamic dataitem within the generated dynamic mobile document. The data processingactivities additionally include transmitting, via the at least onenetwork interface device, the generated dynamic mobile documentaccording to the identified transmission mode to a network destinationof the network identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a mobile wallet item, according to an exampleembodiment.

FIG. 2 is a logical block diagram of a system architecture, according toan example embodiment.

FIG. 3 includes three process flow diagrams, according to exampleembodiments.

FIG. 4 is a block flow diagram of a method, according to an exampleembodiment.

FIG. 5 is a block flow diagram of a method, according to an exampleembodiment.

FIG. 6 is a block diagram of a computing device, according to an exampleembodiment.

DETAILED DESCRIPTION

Various embodiments herein each include at least one of systems,methods, software, and data structures for dynamic mobile wallet items.Mobile wallet items, which are a form of mobile documents, typicallyinclude barcodes and are used for airline boarding passes, movie andevent tickets, mobile documents, coupons, vouchers, and the like thatare delivered to and stored locally on a mobile device itself. Whendelivered to a consumer mobile device, the mobile wallet item normallyconsists of more than just the barcode. For instance, a company logo andsome clear text information may be displayed. To date, the elements of amobile wallet item have generally been static. The various embodimentsherein make one or more of the elements of a mobile wallet item dynamic,for example to allow for flight status change updates to airlineboarding passes, theater or venue changes for movie and event tickets,and other changes that are relevant in the context of a specific mobilewallet item type. Some such embodiments include updating mobile walletitem elements stored on a mobile device, while other embodiments includeretrieving or receiving a new copy or version of the mobile wallet itemthat has been updated on a server. Other embodiments may include acombination of such updating techniques.

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of illustration specific embodiments in which the inventive subjectmatter may be practiced. These embodiments are described in sufficientdetail to enable those skilled in the art to practice them, and it is tohe understood that other embodiments may be utilized and thatstructural, logical, and electrical changes may be made withoutdeparting from the scope of the inventive subject matter. Suchembodiments of the inventive subject matter may be referred to,individually and/or collectively, herein by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed.

The following description is, therefore, not to be taken in a limitedsense, and the scope of the inventive subject matter is defined by theappended claims.

The functions or algorithms described herein are implemented inhardware, software or a combination of software and hardware in oneembodiment. The software comprises computer executable instructionsstored on computer readable media such as memory or other type ofstorage devices. Further, described functions may correspond to modules,which may be software, hardware, firmware, or any combination thereof.Multiple functions are performed in one or more modules as desired, andthe embodiments described are merely examples. The software is executedon a digital signal processor, ASIC, microprocessor, or other type ofprocessor operating on a system, such as a personal computer, server, arouter, or other device capable of processing data including networkinterconnection devices.

Some embodiments implement the functions in two or more specificinterconnected hardware modules or devices with related control and datasignals communicated between and through the modules, or as portions ofan application-specific integrated circuit. Thus, the exemplary processflow is applicable to software, firmware, and hardware implementations.

FIG. 1 illustrates a mobile wallet item 102, according to an exampleembodiment. The mobile wallet item 102 is one example embodiment of adynamic mobile document as also referred to herein. The illustratedmobile wallet item 102 is an airline boarding pass that may be used togain entry to a flight, pass through airport security, gain entry to anairline lounge, and other possible uses. The mobile wallet item 102 is amobile document that may be received on a mobile device and viewedwithin a mobile wallet app, such as the “WALLET” app on IPHONE® devicesavailable from APPLE, INC, of Cupertino, Calif. and other apps thatperform similar functions to provide ready access to items such ascredit cards, travel service boarding passes, loyalty cards, membershipcards, event tickets, and the like. Regardless of the actual mobilewallet app that is used, the mobile wallet app may contain functionalitynatively or as augmented or extended in some embodiments or augmentedwith the functionality of one or more other apps in some embodiments tofacilitate some of the various embodiments herein. In some embodiments,the mobile wallet item 102 is received and viewable within a specificmobile app, such as a mobile app of an airline, movie theater operator,sporting league, event venue, event ticket retailer, and other suchapps. In some further embodiments, the mobile wallet item 102 may beviewed within more than one mobile app, within a document viewing app,within an image viewing app, within an email or text message, and thelike.

The mobile wallet item 102 includes several elements, some of which maybe dynamic. One element is the “GoFast Airlines” header or logo. Thereare also three other dynamic elements 104, 106, 108 of the mobile walletitem 102, although other mobile wallet items and other mobile documentsmay include only one dynamic element or many dynamic elements. Thedynamic elements of the mobile wallet item include a barcode 104, flightinformation 106, and an indicator 108 of when the mobile wallet item102, or one or more of the dynamic elements therein, was last updated.In some embodiments, the indicator 108 may not be visible, but insteadutilized by an update process of a mobile wallet app to determine whento check for updates to the mobile wallet item 102, such as everyfifteen minutes, every two hours, daily, or another period. The refreshperiod for the mobile wallet item 102 may be specified within a mobilewallet or other app used to view the mobile wallet item 102, withinmetadata 102M of the mobile wallet item, within metadata. 104M, 106M ofone or more dynamic elements 104, 106, or multiple such locations.Regardless, the dynamic elements 104, 106 are data items that can changeover time while the mobile wallet item 102 resides on a mobile device.

Mobile wallet items 102, such as travel boarding passes as illustratedor movie tickets, sporting event tickets, and the like, often involveunderlying data that may change. Airport gate assignments, flightstatus, boarding times, sporting event start times and weather delays,seat assignments, theater complex theater assignments, and the like maychange and static mobile wallet items are unable to accommodate suchchanges, thereby requiring new static mobile wallet items be issued andobtained or replace paper items be generated and provided. The variousembodiments herein allow for the dynamic elements 104, 106 to be updatedor for the entire mobile wallet item 102 to be updated. The updates mayoccur in different embodiments in different ways. For example, a mobilewallet app may include code that operates to refresh data of dynamicelements 104, 106 by retrieving updated data from one or more datasources as identified within metadata 102M, 104M, 106M of a mobilewallet item or as may be transmitted thereto. In other embodiments, oneor more other apps may feed updated data to the mobile wallet app.

In some embodiments, metadata 102M, 104M, 106M underlies one or more ofthe mobile wallet item 102 and dynamic elements 104, 106. The metadatamay define how the data is to be presented, link the data of therespective dynamic element to a callable application programminginterface (API), web service, or other network location from which anupdate to the respective data may be requested, set the refresh period,and other purposes.

FIG. 2 is a logical block diagram of a system architecture 200,according to an example embodiment. The system architecture 200 includesan operator system 212, a cloud service provider system 214, and anynumber of consumer computing devices, such as personal computers 210 andmobile devices, such as smartphones 202, smartwatch 204, tablet 206,among others. These elements of the system architecture 200 aregenerally connected via one or more networks 208, which includes theInternet in many embodiments. Note that some mobile devices, such as thesmartwatch 204, may no connect directly to the network 208 and insteadconnect via a BLUETOOTH® connection 216 to another device, such as thesmartphone 202.

The operator system 212 is an example of a system implemented by anoperator of a service or facility for which a dynamic mobile document,such as the mobile wallet item 102 of FIG. 1, is provided. The operatorsystem 212 may therefore be a passenger flight reservation andoperations system of an airline, a ticket purchasing and issuing systemof a theater or venue operator, and the like The operator system 212 istherefore generally a system that maintains and generates data that isincluded in a mobile document. The cloud service provider system 214 isa system that provides mobile document generation and update services tothe operator system 212 and to apps 220, 222 that are present onconsumer devices. In some embodiments, the cloud service provider system214 receives data from the operator system 212 to generate mobiledocuments and to transmit them to the consumer devices or return them tothe operator system 212 to provide them to the consumer devices. Thecloud service provider system 214 may also provide updates to dynamicmobile documents when requested by the consumer devices directly orindirectly via the operator system 212.

The consumer devices 220, 222 may include one or both of an operator app220 and a wallet app 222. The operator app 220 is a mobile device appthat communicates over the network 208 with one or both of the operatorsystem 212 and the cloud service provider system to request and receivedynamic mobile documents and updates to to dynamic elements thereof. Theoperator app 220 may store and present dynamic mobile documents and alsoprovide them to the wallet app 222. The wallet app 222 may receivedynamic mobile documents and store and present them. Dynamic mobiledocuments may also be received via email, text message, and otherelectronic means in some embodiments which may then be imported to oneor both of the operator app 220 and the wallet app 222. The operator app220 and the wallet app 222 may also request and receive dynamic mobiledocument updates from one or both of the operator system 212 and cloudservice provider system 214. Note that some mobile documents may alsoinclude dynamic elements with data sourced from other network 208locations, such as weather data which may be requested and received froma weather service provider (not illustrated), destination guide datasources (not illustrated), advertising content providers (notillustrated), and other data sources.

Although the operator system 212 and the cloud service provider system214 are illustrated as separate and distinct systems, these systems maybe combined into a single system in some embodiments. Further, in someembodiments, the cloud service provider system 214 is operated by athird-party and is a multi-tenant system providing services for aplurality of operator system 212. In other embodiments, the cloudservice provider system 214 is operated by the same entity as theoperator system 212.

FIG. 3 includes three process flow diagrams 1, 2, and 3, according toexample embodiments. The first process flow diagram 1 illustrates anexample embodiment of a process whereby a mobile device app, such as theoperator app 220 of FIG. 2, requests a dynamic mobile document from aservice provider, such as the operator system 212 of FIG. 2. The processflow diagram 2 of FIG. 3 illustrates an example embodiment of a processthrough which the mobile device app receives an update to a dynamicmobile document pushed by the service provider. The process of flowdiagram 3 illustrates an example embodiment of a process through which amobile device app requests, or pulls, an update to a dynamic mobiledocument from the service provider, although in other embodiments, therequest may instead be sent to a dynamic servicer, such as the cloudservice provider system 214 of FIG. 2.

The first process flow diagram 1, as mentioned above, 1 illustrates anexample embodiment of a process whereby a mobile device app requests adynamic mobile document from a service provider. The mobile device appsends a request for a mobile document to the service provider. Theservice provider then retrieves and generates data for the requestedmobile document and sends the data to the dynamic server. The dynamicserver then stores the mobile document data, generates the mobiledocument including a barcode (e.g., a Quick Response code, standardone-dimensional barcode) when needed for the document-type requested,and sends the generated mobile document to the requesting mobile deviceapp. Note however that sending the mobile document to the mobile deviceapp may include sending a link in an email, text message, in-appmessage, and the like or an image of the mobile document. In someembodiments, the dynamic servicer may return the generated mobiledocument to the service provider for relay back to the mobile deviceapp.

The second process flow diagram 2, as mentioned above, illustrates anexample embodiment of a process through which the mobile device appreceives an update to a dynamic mobile document pushed by the serviceprovider. Over time, data from which the mobile document was generatedmay change. For example, when the mobile document is an airline serviceboarding pass, the gate assignment for boarding of the flight may changeon the service provider system. The service provider system will sendthe updated data to the dynamic servicer. The data sent to the dynamicservicer may not identify individual boarding passes to receive theupdate, but instead include sufficient data to identify the flight, suchas a flight date, flight number, departure airport, and arrival airportplus a data representation of the newly assigned gate. As the dynamicservicer stores the data from which it generates the mobile documentsare generated, the dynamic servicer is then able to identify to whichmobile device app instances the mobile document has been sent withinthat data and then provide the update appropriately. Thus, when thedynamic servicer receives a data update from the service provider, thedynamic servicer stores the updated data, identifies to whom the updateis to be provided when not specified in the received data, and generatesand sends the update to one or more mobile devices apps, which asmentioned above may instead be text messages, emails, in-app messages,and the like.

The third process flow diagram 3 illustrates an example embodiment of aprocess through which a mobile device app requests, or pulls, an updateto a dynamic mobile document from the service provider. This processflow begins with the mobile device app requesting an update to a mobiledocument, either as a whole or with regard to one or more specificdynamic elements included in the mobile document. The update request issent to the service provider. The service provider then retrieves therequested data when the data has been updated since the mobile documentwas generated and sends the data to the dynamic servicer. The dynamicservicer then generates the mobile document update, stores the updateddata, and sends the mobile document update to the mobile device app.

FIG. 4 is a block flow diagram of a method 400, according to an exampleembodiment. The method 400 is an example of a method performed by anoperator system or service provider system, such as operator system 212of FIG. 2 or the furthest right column of FIG. 3.

In some embodiments, the method 400 includes receiving 400, via anetwork, a dynamic mobile document request associated with a registereduser and including a token associated with data to be included in thedynamic mobile document. The method 400 further includes retrieving 404data for the dynamic mobile document from a database based at least inpart on the token and an identifier of the registered user. Retrieving404 the data for the dynamic mobile document may also include generatingand deriving data in some embodiments. The method 400 then continues bytransmitting, via the network, the retrieved dynamic mobile documentdata and data indicating how the dynamic mobile document is to beprovided to the registered user to a dynamic mobile document generationservice. The dynamic mobile document generation service is a networkaccessible service in some embodiments, that generates and provides thedynamic mobile document to the registered user. Examples of the dynamicmobile document generation service include the cloud service providersystem 214 of FIG. 2 and the middle column of FIG. 3.

In some embodiments of the method 400, at least one data item retrieved404 from the database for the dynamic mobile document is subject tochange. In some such embodiments, the method 400 further includesreceiving, via the network from the dynamic mobile document generationservice, a dynamic mobile document data update request including atleast the token and retrieving at least a portion of the data for thedynamic mobile document from the database. The method 400 in suchembodiments then transmits, via the network, at least the portion of theretrieved data for the dynamic mobile document to the dynamic mobiledocument generation service.

In some other embodiments of the method 400, at least one data itemretrieved from the database for the dynamic mobile document is subjectto change. The method 400 in such embodiments further includesidentifying a change in the database to a data item included in at leastone dynamic mobile document and retrieving the changed data andadditional data to enable the dynamic mobile document generation serviceto identify all dynamic mobile documents impacted by the changed data.The method 400 in these embodiments then transmits the retrieved changedata and the additional data via the network to the dynamic mobiledocument generation service to provide an update to a dynamic mobiledocument of at least one registered user.

In some embodiments of the method 400, the dynamic mobile documentrequest is received 402 from a mobile device app of the registered user.Some such embodiments further include receiving, via the network fromthe mobile device app or a mobile wallet app of the registered user, adynamic mobile document data update request including at least thetoken. These embodiments may then retrieve at least a portion of thedata for the dynamic mobile document from the database and transmit, viathe network, at least the portion of the retrieved data for the dynamicmobile document to the dynamic mobile document generation service toprovide to the mobile device app or the mobile wallet app from which therequest was received.

In some of these and other embodiments of the method 400, the dynamicmobile document is an airline boarding pass and the token is one or acombination of airline boarding pass data items that uniquely identifyat least one of the airline boarding pass and a flight associatedtherewith. In other embodiments, the dynamic mobile document is a ticketfor admittance to a movie, a sporting event, or other event and thetoken is one or a combination of data items that uniquely identify thedynamic mobile document.

FIG. 5 is a block flow diagram of a method 500, according to an exampleembodiment. The method 500 is an example of a method performed togenerate dynamic mobile documents as may be performed, for example, onthe cloud service provider system 214 of FIG. 2. The method 5000includes receiving 502, via a network from a data source, a dynamicmobile document generation request including data identifying atransmission mode for transmitting a dynamic mobile document to begenerated, a network identifier of where to send the generated dynamicmobile document, and at least one data item to be included in thedynamic mobile document when generated and to uniquely identify thedynamic mobile document. The method 500 further includes storing 504data of the dynamic mobile document generation request in a database andgenerating 506 the dynamic mobile document including the at least onedata item and metadata defining the at least one item as a dynamic dataitem within the generated dynamic mobile document. The method 500continues by transmitting 508, via the network, the generated dynamicmobile document according to the identified transmission mode to anetwork destination of the network identifier.

In some embodiments of the method 500, the metadata defining the atleast one data item as a dynamic data item further includes metadataassociating the respective at least one data item with a network servicethat is callable from a mobile device via the network to retrieve anupdate of the respective at least one data item. The metadata in suchembodiments informs a refresh process of a mobile wallet app or one ormore other apps on the mobile device of a network location or processthat is callable to obtain the updated data or from which updated datamay be pushed to the mobile device. The updated data in some embodimentsmay not be retrieved, but rather an indication of the dynamic databecoming outdated indicating that the user should select a link toobtain a new mobile wallet item to including the updated data.

In some embodiments of the method 500, the data identifying thetransmission mode identifies at least one of a text message or emailthat includes a Universal Resource Identifier from which the dynamicmobile document may be retrieved, a mobile device in-app message thatincludes the dynamic mobile document or a URI from which an app willretrieve the dynamic mobile document, an email that includes the dynamicmobile document therein or as an attachment. In some such embodiments,the dynamic mobile document is viewable within at least one of a mobilewallet app, a mobile app, a web browser, an image viewing app, and adocument viewing app.

In some embodiments of the method 500, the dynamic mobile documentincludes at least one dynamic data element and a date-time stampincluding date and time data of when each of the at least one dynamicdata elements was last updated in the dynamic mobile document.

In some other embodiments, the method 500 includes receiving, via thenetwork from the data source, such as the operator system 212 of FIG. 2,an update of at least one dynamic mobile document data item and dataassociating the at least one updated data item to at least one mobiledocument. The method 500 in such embodiments stores the updated at leastone dynamic mobile document data item in the database in associationwith each of the at least one mobile documents. The storing of theupdated at least one dynamic mobile document data item may includestoring an indicator of each of the at least one updated dynamic mobiledocument items.

Another embodiment of the method 500 includes receiving, via the networkfrom a mobile device, a dynamic mobile document update request includingdata uniquely identifying the dynamic mobile document to be updated andretrieving each of the at least one updated mobile document data itemsfor the dynamic mobile document from the database based at least in parton the data uniquely identifying the dynamic mobile document to beupdated. The method 500 in such embodiments then transmits, via thenetwork, the retrieved at least one updated mobile document data item tothe mobile device.

In another embodiment of the method 500, the received 502 dynamic mobiledocument generation request is a request to generate a dynamic mobileboarding pass for a transportation service segment. In such embodiments,the at least one data item to be included in the dynamic mobile documentwhen generated and to uniquely identify the dynamic mobile documentincludes a transportation segment identifier, a boarding time, and adeparture time. In some such embodiments, an update of the at least onedynamic mobile document data item includes an update with regard to atleast one of the transportation segment identifier, the boarding time,and the departure time. In some such embodiments, the method 500 furtherincludes, upon receipt of the update of the at least one of thetransportation segment identifier, the boarding time, and the departuretime, identifying all generated dynamic mobile documents for which datais stored in the database in association with the travel segment forwhich the update pertains. Such embodiments then generate and transmit,via the network, a dynamic mobile document update to the networkdestinations stored in the database to which the dynamic mobiledocuments were transmitted.

FIG. 6 is a block diagram of a computing device, according to an exampleembodiment. In one embodiment, multiple such computer systems areutilized in a distributed network to implement multiple components in atransaction-based environment. An object-oriented, service-oriented, orother architecture may be used to implement such functions andcommunicate between the multiple systems and components. One examplecomputing device in the form of a compute 610, may include a processingunit 602, memory 604, removable storage 612, and non-removable storage614. Although the example computing device is illustrated and describedas computer 610, the computing device may be in different forms indifferent embodiments. For example, the computing device may instead bea smartphone, a tablet, smartwatch, or other computing device includingthe same or similar elements as illustrated and described with regard toFIG. 6. Devices such as smartphones, tablets, and smartwatches aregenerally collectively referred to as mobile devices. Further, althoughthe various data storage elements are illustrated as part of thecomputer 610, the storage may also or alternatively include cloud-basedstorage accessible via a network, such as the Internet.

Returning to the computer 610, memory 604 may include volatile memory606 and non-volatile memory 608. Computer 610 may include—or have accessto a computing environment that includes a variety of computer-readablemedia, such as volatile memory 606 and non-volatile memory 608,removable storage 612 and non-removable storage 614. Computer storageincludes random access memory (RAM), read only memory (ROM), erasableprogrammable read-only memory (EPROM) and electrically erasableprogrammable read-only memory (EEPROM), flash memory or other memorytechnologies, compact disc read-only memory (CD ROM), Digital VersatileDisks (DVD) or other optical disk storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium capable of storing computer-readable instructions.

Computer 610 may include or have access to a computing environment thatincludes input 616, output 618, and a communication connection 620. Theinput 616 may include one or more of a touchscreen, touchpad, mouse,keyboard, camera, one or more device-specific buttons, one or moresensors integrated within or coupled via wired or wireless dataconnections to the computer 610, and other input devices. The computer610 may operate in a networked environment using a communicationconnection 620 to connect to one or more remote computers, such asdatabase servers, web servers, and other computing device. An exampleremote computer may include a personal computer (PC), server, router,network PC, a peer device or other common network node, or the like. Thecommunication connection 620 may be a network interface device such asone or both of an Ethernet card and a wireless card or circuit that maybe connected to a network. The network may include one or more of aLocal Area Network (LAN), a Wide Area Network (WAN), the Internet, andother networks. In some embodiments, the communication connection 620may also or alternatively include a transceiver device, such as aBLUETOOTH® device that enables the computer 610 to wirelessly receivedata from and transmit data to other BLUETOOTH® devices.

Computer-readable instructions stored on a computer-readable medium areexecutable by the processing unit 602 of the computer 610. A hard drive(magnetic disk or solid state), CD-ROM, and RAM are some examples ofarticles including a non-transitory computer-readable medium. Forexample, various computer programs 625 or apps, such as one or moreapplications and modules implementing one or more of the methodsillustrated and described herein or an app or application that executeson a mobile device or is accessible via, a web browser, may be stored ona non-transitory computer-readable medium.

It will be readily understood to those skilled in the art that variousother changes in the details, material, and arrangements of the partsand method stages which have been described and illustrated in order toexplain the nature of the inventive subject matter may be made withoutdeparting from the principles and scope of the inventive subject matteras expressed in the subjoined claims.

What is claimed is:
 1. A method comprising: receiving, via a network, adynamic mobile document request associated with a registered user andincluding a token associated with data to be included in the dynamicmobile document; retrieving data for the dynamic mobile document from adatabase based at least in part on the token and an identifier of theregistered user; and transmitting, via the network, the retrieveddynamic mobile document data and data indicating how the dynamic mobiledocument is to be provided to the registered user to a dynamic mobiledocument generation service, the dynamic mobile document generationservice to generate and provide the dynamic mobile document to theregistered user.
 2. The method of claim 1, wherein at least one dataitem retrieved from the database for the dynamic mobile document issubject to change, the method further comprising: receiving, via thenetwork from the dynamic mobile document generation service, a dynamicmobile document data update request including at least the token;retrieving at least a portion of the data for the dynamic mobiledocument from the database; and transmitting, via the network, at leastthe portion of the retrieved data for the dynamic mobile document to thedynamic mobile document generation service.
 3. The method of claim 1,wherein at least one data item retrieved from the database for thedynamic mobile document is subject to change, the method furthercomprising: identifying a change in the database to a data item includedin at least one dynamic mobile document; retrieving the changed data andadditional data to enable the dynamic mobile document generation serviceto identify all dynamic mobile documents impacted by the changed data;and transmitting the retrieved change data and the additional data viathe network to the dynamic mobile document generation service to providean update to a dynamic mobile document of at least one registered user.4. The method of claim 1, wherein the dynamic mobile document request isreceived from a mobile device app of the registered user.
 5. The methodof claim 4, further comprising: receiving, via the network from themobile device app or a mobile wallet app of the registered user, adynamic mobile document data update request including at least thetoken; retrieving at least a portion of the data for the dynamic mobiledocument from the database; and transmitting, via the network, at leastthe portion of the retrieved data for the dynamic mobile document to thedynamic mobile document generation service to provide to the mobiledevice app or the mobile wallet app from which the request was received.6. The method of claim 1, wherein the dynamic mobile document is anairline boarding pass and the token is one or a combination of airlineboarding pass data items that uniquely identify at least one of theairline boarding pass and a flight associated therewith.
 7. A methodcomprising: receiving, via a network from a data source, a dynamicmobile document generation request including data identifying atransmission mode for transmitting a dynamic mobile document to begenerated, a network identifier of where to send the generated dynamicmobile document, and at least one data item to be included in thedynamic mobile document when generated and to uniquely identify thedynamic mobile document; storing data of the dynamic mobile documentgeneration request in a database; generating the dynamic mobile documentincluding the at least one data item and metadata defining the at leastone item as a dynamic data item within the generated dynamic mobiledocument; and transmitting, via the network, the generated dynamicmobile document according to the identified transmission mode to anetwork destination of the network identifier.
 8. The method of claim 7,wherein the data identifying the transmission mode identifies at leastone of a text message or email that includes a Universal ResourceIdentifier from which the dynamic mobile document may be retrieved, amobile device in-app message that includes the dynamic mobile documentor a URI from which an app will retrieve the dynamic mobile document, anemail that includes the dynamic mobile document therein or as anattachment.
 9. The method of claim 8, wherein the dynamic mobiledocument is viewable within at least one of a mobile wallet app, amobile app, a web browser, an image viewing app, and a document viewingapp.
 10. The method of claim 7, wherein the dynamic mobile documentincludes at least one dynamic data element and a date-time stampincluding date and time data of when each of the at least one dynamicdata elements was last updated in the dynamic mobile document.
 11. Themethod of claim 7, further comprising: receiving, via the network fromthe data source, an update of at least one dynamic mobile document dataitem and data associating the at least one updated data item to at leastone mobile document; and storing the updated at least one dynamic mobiledocument data item in the database in association with each of the atleast one mobile documents.
 12. The method of claim 11, wherein thestoring of the updated at least one dynamic mobile document data itemincludes storing an indicator of each of the at least one updateddynamic mobile document items.
 13. The method of claim 11, furthercomprising: receiving, via the network from a mobile device, a dynamicmobile document update request including data uniquely identifying thedynamic mobile document to be updated; retrieving each of the at leastone updated mobile document data items for the dynamic mobile documentfrom the database based at least in part on the data uniquelyidentifying the dynamic mobile document to be updated; and transmitting,via the network, the retrieved at least one updated mobile document dataitem to the mobile device.
 14. The method of claim 11, wherein: thedynamic mobile document generation request is a request to generate adynamic mobile boarding pass for a transportation service segment; theat least one data item to be included in the dynamic mobile documentwhen generated and to uniquely identify the dynamic mobile documentincludes a transportation segment identifier, a boarding time, and adeparture time; the update of the at least one dynamic mobile documentdata item includes an update with regard to at least one of thetransportation segment identifier, the boarding time, and the departuretime; and the method further comprises: upon receipt of the update ofthe at least one of the transportation segment identifier, the boardingtime, and the departure time, identifying all generated dynamic mobiledocuments for which data is stored in the database in association withthe travel segment for which the update pertains; and generating andtransmitting, via the network, a dynamic mobile document update to thenetwork destinations stored in the database to which the dynamic mobiledocuments were transmitted.
 15. The method of claim 7, wherein themetadata defining the at least one data item as a dynamic data itemfurther includes metadata associating the respective at least one dataitem with a network service that is callable from a mobile device viathe network to retrieve an update of the respective at least one dataitem.
 16. A system comprising: at least one computer processor; at leastone memory device; at least one network interface device; a databaseunder management by a database management system stored on the at leastone memory device or accessible via that at least one network interfacedevice, the database storing dynamic mobile document data received fromat least one data source; a dynamic mobile document generation modulestored in the at least one memory device and executable by the at leastone processor to perform data processing activities comprising:receiving, via the at least one network interface device from the atleast one data source, a dynamic mobile document generation requestincluding data identifying a transmission mode for transmitting adynamic mobile document to be generated, a network identifier of whereto send the generated dynamic mobile document, and at least one dataitem to be included in the dynamic mobile document when generated and touniquely identify the dynamic mobile document; storing data of thedynamic mobile document generation request in the database; generatingthe dynamic mobile document including the at least one data item andmetadata defining the at least one item as a dynamic data item withinthe generated dynamic mobile document; and transmitting, via the atleast one network interface device, the generated dynamic mobiledocument according to the identified transmission mode to a networkdestination of the network identifier.
 17. The system of claim 16,further comprising: a dynamic mobile document update module stored inthe at least one memory device and executable by the at least oneprocessor to perform data processing activities comprising: receiving,via the at least one network interface device from the at least one datasource, an update of at least one dynamic mobile document data item anddata associating the at least one updated data item to at least onemobile document; and storing the updated at least one dynamic mobiledocument data item in the database in association with each of the atleast one mobile documents.
 18. The system of claim 17, the dataprocessing activities of the dynamic mobile document update modulefurther comprising: receiving, via the at least one network interfacedevice from a mobile device, a dynamic mobile document update requestincluding data uniquely identifying the dynamic mobile document to beupdated; retrieving each of the at least one updated mobile documentdata items for the dynamic mobile document from the database based atleast in part on the data uniquely identifying the dynamic mobiledocument to be updated; and transmitting, via the at least one networkinterface device to the requesting mobile device, the retrieved at leastone updated mobile document data item to the mobile device.
 19. Thesystem of claim 17, wherein: the dynamic mobile document generationrequest received by the dynamic mobile document generation module is arequest to generate a dynamic mobile boarding pass for a transportationservice segment and the at least one data source from which the dynamicmobile document generation request is received is a computing system ofan air service provider; the at least one data item to be included inthe dynamic mobile document when generated dynamic mobile documentgeneration module uniquely identifies the dynamic mobile document andthe at least one data item included in the dynamic mobile documentfurther including a transportation segment identifier, a boarding time,and a departure time; the update of the at least one dynamic mobiledocument data item received by the dynamic mobile document update moduleincludes an update with regard to at least one of the transportationsegment identifier, the boarding time, and the departure time; and thedata processing activities of the dynamic mobile document update modulefurther comprising: upon receipt of the update of the at least one ofthe transportation segment identifier, the boarding time, and thedeparture time, identifying all generated dynamic mobile documents forwhich data is stored in the database in association with the travelsegment for which the update pertains; and. generating and transmitting,via the at least one network interface device, a dynamic mobile documentupdate to the network destinations stored in the database to which thedynamic mobile documents were transmitted..
 20. The system of claim 16,wherein the metadata defining the at least one data item as a dynamicdata item further includes metadata associating the respective at leastone data item with an update service of the dynamic mobile documentupdate module that is callable from a mobile device via the network toretrieve an update of the respective at least one data item